Skip to content

Conversation

@raphlopez
Copy link

Add config and special keep-groups handling required to support the --group-add=group|keep-groups equivalent from the podman CLI. The special keep-groups case allows users to configure the user running within the container process to inherit the groups of the host user.

Closes #390

  • If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Job submissions can now specify arbitrary host groups that the container user should be added to, which weakens the container isolation boundary. Main use case for this is trusted workloads that need access to host resources for e.g. telemetry collection.

Add config and special `keep-groups` handling
required to support the `--group-add=group|keep-groups`
equivalent from the podman CLI.

The special `keep-groups` case allows users to configure
the user running within the container process to inherit
the groups of the host user.
@raphlopez raphlopez requested a review from a team as a code owner January 13, 2026 21:47
@hashicorp-cla-app
Copy link

hashicorp-cla-app bot commented Jan 13, 2026

CLA assistant check
All committers have signed the CLA.

@hashicorp-cla-app
Copy link

CLA assistant check

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

Have you signed the CLA already but the status is still pending? Recheck it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

Accessing devices in rootless containers with --group-add keep-groups

1 participant